Artifact: Test Plan
Purpose
The purpose of the test plan is to communicate the intent of the testing activities. The following people use the test plan:
Brief
Outline
(hyperlinks into HTML template in a new window) 1. Introduction1.1 Purpose1.2 Background1.3 Scope1.4 Project Identification2. Requirements for Test3. Test Strategy3.1 Testing Types3.1.1 Data and Database Integrity Testing3.1.2 Function Testing3.1.3 Business Cycle Testing3.1.4 User Interface Testing3.1.5 Performance Profiling3.1.6 Load Testing3.1.7 Stress Testing3.1.8 Volume Testing3.1.9 Security and Access Control Testing3.1.10 Failover and Recovery Testing3.1.11 Configuration Testing3.1.12 Installation Testing3.2 Tools4. Resources4.1 Workers4.2 System5. Project Milestones6. Deliverables6.1 Test Model6.2 Test Logs6.3 Defect Reports7. Appendix A: Project TasksTiming
The initial test plan is created at the outset of the project, referred to as the "Master Test Plan." As each iteration is planned, a one or more precise "Iteration Test Plan(s)" are created containing more precise data pertaining to the specified iteration. All of the test plans' contents are based upon the Test Plan Templates. See the section Tailoring below. Responsibility
A Test Designer is responsible for the integrity of the Test Plan, ensuring that:
The Test Designer uses the contents of the Test Plan to produce the following related artifacts: Tailoring
The Test Plan (contents and format) may require modification to meet the needs of internal or external standards, guidelines, or oversight. Start with the Test Plan template included with RUP and add, modify, or remove content as needed. The "Master Test Plan," created at the outset of the project may only provide an overview of the total test effort planned. The test plans created during each iteration should contain more precise information related to the specific requirements for test, test strategies, resources, etc. that relate to the specified iteration. |
Rational Unified
Process |